Keep Linux updates within startup health deadline - #34
Conversation
Signed-off-by: Joseph Yaksich <gitcommit90@users.noreply.github.com>
📝 WalkthroughWalkthroughThe release is bumped to 0.0.25, including channel-machine image defaults and documentation. Server bootstrap now prepares durable memory asynchronously so health-port readiness does not wait for optional memory installation. ChangesRelease and runtime updates
Estimated code review effort: 2 (Simple) | ~10 minutes Sequence Diagram(s)sequenceDiagram
participant bootstrap
participant memoryRuntime
participant HTTPServer
bootstrap->>memoryRuntime: Start durable-memory preparation
bootstrap->>HTTPServer: Open health port
memoryRuntime-->>bootstrap: Resolve or reject asynchronously
bootstrap->>bootstrap: Handle preparation errors
Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CHANGELOG.md`:
- Around line 767-768: Remove the stale [0.0.24] compare-link entry from the
changelog, or update it to reference a valid published tag; keep the existing
[Unreleased] and [0.0.25] links unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: b6ec0c31-0699-4da0-a026-5218429bdfda
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (8)
CHANGELOG.mdREADME.mdpackage.jsonsrc/server/channel-computers.tssrc/server/db.tssrc/server/index.tstest/channel-computers.mjstest/desktop.mjs
| [Unreleased]: https://github.com/gitcommit90/1Helm/compare/v0.0.25...HEAD | ||
| [0.0.25]: https://github.com/gitcommit90/1Helm/compare/v0.0.23...v0.0.25 |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Remove the stale 0.0.24 compare link.
The release notes state that 0.0.24 was never tagged or published, but [0.0.24] still points to that nonexistent tag on Line 769. Remove the reference or point it to a valid published target.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@CHANGELOG.md` around lines 767 - 768, Remove the stale [0.0.24] compare-link
entry from the changelog, or update it to reference a valid published tag; keep
the existing [Unreleased] and [0.0.25] links unchanged.
Result\n\nRetained Linux hosts now open the health port without synchronously initializing every resident memory database, so real systemd updates stay within their bounded health window. Memory remains initialized for newly created agents and lazily on memory operations.\n\nThis advances the unpublished 0.0.24 candidate to 0.0.25 and retains all Linux/Windows terminal-runtime corrections merged in #33.\n\n## Verification\n\n- npm run typecheck\n- npm run build\n- npm test: 125 native assertions + 110 runnable Node/browser contracts passed; 2 environment-only skips\n- npm run test:onboarding-browser: 20 passed\n- git diff --check
Summary by CodeRabbit